CI of azps-14.6.0 #3740

huypub · 2025-11-03T19:39:18Z

PR Summary

PR Checklist

Descriptive Title: This PR's title is a synopsis of the changes it proposes.
Summary: This PR's summary describes the scope and intent of the change.
Contributor's Guide: I have read the contributors guide.
Style: This PR adheres to the style guide.

Build.Reason:Manual by Huaping Yu (BEYONDSOFT CONSULTING INC) Build.Url:https://apidrop.visualstudio.com/Content%20CI/_build/results?buildId=574961&view=results

learn-build-service-prod · 2025-11-03T19:45:26Z

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

#	File	Term	Line	Sev	AI Recommendation	Class	AI Review Details
1	azps-14.6.0\Az.Security\Get-AzSecurityAdaptiveApplicationControlGroup.md	whitelist	36	2	No action needed	Diversity	Details The term `whitelist` appears as a component of resource type and property names such as 'applicationWhitelistings' and 'Microsoft.Security/applicationWhitelistings'. According to the rules, when the word is a component of other words, such as in resource names, it does not need to be replaced or removed.

2	azps-14.6.0\Az.Support\New-AzSupportTicket.md	country	267	2	Replacement required	Geopolitical	Details The term `country` is used to label a parameter that collects the user's country information, which is a scenario where geopolitical sensitivity is relevant. To avoid issues, it should be replaced with `country/region`.

3	azps-14.6.0\Az.Support\Update-AzSupportTicket.md	country	134	2	Replacement required	Geopolitical	Details The term `country` is used to describe a user attribute in a parameter description, which likely refers to the user's geographic location. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.

4	azps-14.6.0\Az.Security\Get-AzSecurityAdaptiveApplicationControl.md	whitelist	34	2	No action needed	Diversity	Details The term `whitelist` appears only as a component of resource type names and file paths, such as 'applicationWhitelistings' and in output examples. According to the rules, when the word is a component of other words or appears in file paths, it does not need to be replaced or removed.
5	azps-14.6.0\Az.Security\Get-AzSecurityAdaptiveApplicationControl.md	whitelist	46	2	No action needed	Diversity	Details The term `whitelist` appears only as a component of resource type and property names, such as 'applicationWhitelistings' and not as a descriptive label or documentation text. According to the rules, when the word is a component of other words (e.g., in resource names, file paths, or property names), it does not need to be replaced or removed.

6	azps-14.6.0\Az.Peering\Get-AzPeeringServiceLocation.md	country	61	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and in documentation to label a filter for peering service locations, which is effectively labeling a country/region list or resource. To avoid geopolitical issues, it should be replaced with `country/region` throughout the documentation and parameter naming for clarity and inclusivity.
7	azps-14.6.0\Az.Peering\Get-AzPeeringServiceLocation.md	country	84	2	Replacement required	Geopolitical	Details The term `country` is used to label a country/region list and as a parameter for filtering locations by country. To avoid geopolitical issues and be inclusive, it should be replaced with `country/region` throughout the documentation and parameter descriptions.
8	azps-14.6.0\Az.Peering\Get-AzPeeringServiceLocation.md	country	89	2	Replacement required	Geopolitical	Details The term `country` is used to label a parameter that specifies a geographic location, which can be interpreted as labeling a country/region list or resource. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.

9	azps-14.6.0\Az.Peering\Get-AzPeeringServiceCountry.md	countries	27	2	Replacement required	Geopolitical	Details The term `countries` is used to label a list of geographic locations for a service, which can raise geopolitical sensitivity. It should be replaced with `countries/regions` to be inclusive and avoid issues.
10	azps-14.6.0\Az.Peering\Get-AzPeeringServiceCountry.md	Hong Kong	43	2	Replacement required	Geopolitical	Details The term `Hong Kong` is used as an entry in a list of countries for a service, which is a formal context. To avoid geopolitical issues and ensure accuracy, it should be replaced with `Hong Kong SAR` or `Hong Kong Special Administrative Region`.
11	azps-14.6.0\Az.Peering\Get-AzPeeringServiceCountry.md	countries	53	2	Replacement required	Geopolitical	Details The term `countries` is used to label a list of geographic locations for a service, which can raise geopolitical sensitivity. It should be replaced with `countries/regions` to be inclusive and avoid issues.

12	azps-14.6.0\Az.Peering\Az.Peering.md	countries	50	2	Replacement required	Geopolitical	Details The term `countries` is used to label a list of available countries for peering service, which is a resource label scenario. To avoid geopolitical issues, it should be replaced with `countries/regions`.

13	azps-14.6.0\Az.Oracle\Get-AzOracleAutonomousDatabase.md	whitelist	104	2	No action needed	Diversity	Details The term `whitelist` appears as part of the property name `WhitelistedIP`, which is a field name in the output of the cmdlet. According to the rules, when referring to a field or property name, it does not need to be replaced or removed.

14	azps-14.6.0\Az.Oracle\New-AzOracleAutonomousDatabase.md	whitelist	737	2	Replacement required	Diversity	Details The term `whitelist` is used as a parameter name and description for an IP access control list, which is a list of approved IPs. This fits the rule for describing a list of things that have received approval or are considered to be in good favor. It should be replaced with `allow list` or a more specific term such as `approved IP list` to avoid sensitive terminology.

15	azps-14.6.0\Az.Network\Set-AzFirewallPolicyDraft.md	whitelist	32	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter name (`ThreatIntelWhitelist`) and as a component in object names (e.g., `PSAzureFirewallPolicyThreatIntelWhitelist`). According to the rules, when the word is referring to a field, parameter, or property name, it does not need to be replaced or removed.
16	azps-14.6.0\Az.Network\Set-AzFirewallPolicyDraft.md	whitelist	43	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter/property name (`ThreatIntelWhitelist`), which is a field name in the API and code. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
17	azps-14.6.0\Az.Network\Set-AzFirewallPolicyDraft.md	whitelist	83	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter name (`ThreatIntelWhitelist`) and as a component in a PowerShell object name (`PSAzureFirewallPolicyThreatIntelWhitelist`). According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
18	azps-14.6.0\Az.Network\Set-AzFirewallPolicyDraft.md	whitelist	376	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter name (`ThreatIntelWhitelist`) and as a component in a PowerShell object name (`PSAzureFirewallPolicyThreatIntelWhitelist`). According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.

19	azps-14.6.0\Az.Network\Set-AzFirewallPolicy.md	whitelist	33	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter and type name (`ThreatIntelWhitelist`, `PSAzureFirewallPolicyThreatIntelWhitelist`) in PowerShell cmdlet documentation, which is a field/property name. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
20	azps-14.6.0\Az.Network\Set-AzFirewallPolicy.md	whitelist	33	2	No action needed	Diversity	Details The term `whitelist` is used as a parameter/property name in PowerShell cmdlet syntax and object definitions, which is a field name scenario. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
21	azps-14.6.0\Az.Network\Set-AzFirewallPolicy.md	whitelist	46	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter name and type in PowerShell cmdlet documentation, specifically `ThreatIntelWhitelist` and `PSAzureFirewallPolicyThreatIntelWhitelist`. This is a field/property name in code, and according to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
22	azps-14.6.0\Az.Network\Set-AzFirewallPolicy.md	whitelist	46	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter/property name (`ThreatIntelWhitelist`, `PSAzureFirewallPolicyThreatIntelWhitelist`, `$threatIntelWhitelist`) in code and documentation, which aligns with industry naming conventions and consistency. According to the rules, when industry naming conventions or consistency make replacement of the term impractical, the term should be left unchanged.
23	azps-14.6.0\Az.Network\Set-AzFirewallPolicy.md	whitelist	77	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter name and type (e.g., ThreatIntelWhitelist, PSAzureFirewallPolicyThreatIntelWhitelist) in PowerShell cmdlet documentation, which is a field/property name. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.

24	azps-14.6.0\Az.Network\Set-AzFirewall.md	whitelist	294	2	No action needed	Diversity	Details The term `whitelist` appears as part of property names such as ThreatIntelWhitelist and ThreatIntelWhitelistText, which are field or filter names in code or configuration. According to the guidelines, when the word is used as a field, property, or parameter name, it does not need to be replaced or removed.

25	azps-14.6.0\Az.Network\New-AzNetworkManagerSecurityAdminConfiguration.md	nip	95	2	No action needed	Diversity	Details The term `nip` is used in the context of 'NIP based services', which appears to be an acronym or technical term related to network services, not referring to a person or an offensive context. Therefore, it does not need to be replaced or removed.

26	azps-14.6.0\Az.Network\New-AzFirewallThreatIntelWhitelist.md	whitelist	4	2	No action needed	Diversity	Details The term `whitelist` is used as part of a cmdlet name, parameter name, and object name in PowerShell documentation, which follows industry naming conventions and established API consistency. Changing it would break backward compatibility and established usage.
27	azps-14.6.0\Az.Network\New-AzFirewallThreatIntelWhitelist.md	whitelist	18	2	No action needed	Diversity	Details The term `whitelist` is used as part of a PowerShell cmdlet name, parameter name, and output type, which are industry-standard naming conventions and part of legacy code. Changing these names would break backward compatibility and disrupt user workflows.

28	azps-14.6.0\Az.Network\New-AzFirewallPolicyDraft.md	whitelist	61	2	No action needed	Diversity	Details The term `whitelist` is used as a parameter/property name (ThreatIntelWhitelist, PSAzureFirewallPolicyThreatIntelWhitelist) in code and documentation, which falls under the exception for field or parameter names. According to the guidelines, terms used as field, filter, or parameter names do not need to be replaced or removed.

29	azps-14.6.0\Az.Network\New-AzFirewallPolicy.md	whitelist	19	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter name (`ThreatIntelWhitelist`) and a type name (`PSAzureFirewallPolicyThreatIntelWhitelist`) in PowerShell cmdlet documentation. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed, even if the term is sensitive.
30	azps-14.6.0\Az.Network\New-AzFirewallPolicy.md	whitelist	50	2	No action needed	Diversity	Details The term `whitelist` appears as part of parameter and type names (e.g., ThreatIntelWhitelist, PSAzureFirewallPolicyThreatIntelWhitelist) in PowerShell cmdlet documentation, which are established industry naming conventions and API surface. Changing these would break compatibility and is not practical.

31	azps-14.6.0\Az.Network\Get-AzNetworkWatcherReachabilityProvidersList.md	country	34	2	No action needed	Geopolitical	Details The term `country` is used as a parameter name in a PowerShell cmdlet, which is a field name in code and not a user-facing label or documentation text. According to the rules, when referring to a field or filter name, database name, parameter name, panel name, property name, file name or some other names, it doesn't need to be replaced/removed.

32	azps-14.6.0\Az.Monitor\New-AzAutoscaleProfileObject.md	Cape Verde	121	2	Replacement required	Geopolitical	Details The term `Cape Verde` is used in a user-facing list of time zones, which refers to the country. According to the rule, it should be replaced with the modern, official name to avoid outdated or insensitive terminology. Suggest replacing it with `Cabo Verde Standard Time`.

33	azps-14.6.0\Az.DataMigration\New-AzDataMigrationSelectedDBObject.md	countries	45	2	No action needed	Geopolitical	Details The term `countries` is used as a table name within a database context, specifically in the output of a PowerShell command showing table mappings. According to the rules, when referring to a field or filter name, database name, parameter name, panel name, property name, file name or some other names, it does not need to be replaced or removed.
34	azps-14.6.0\Az.DataMigration\New-AzDataMigrationSelectedDBObject.md	countries	45	2	No action needed	Geopolitical	Details The term `countries` is used as a table name within a database context, specifically in the output of a PowerShell command showing table mappings. According to the rules, when referring to a field or filter name, database name, parameter name, panel name, property name, file name or some other names, it does not need to be replaced or removed.

35	azps-14.6.0\Az.Informatica\New-AzInformaticaOrganization.md	country	146	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and description to capture the country name for a company, which can be interpreted as labeling a country/region resource. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.

36	azps-14.6.0\Az.EdgeOrder\New-AzEdgeOrderShippingAddressObject.md	country	98	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and description for specifying a location in a shipping address object. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.

37	azps-14.6.0\Az.DataBoxEdge\New-AzDataBoxEdgeOrder.md	country	31	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and in documentation to collect address information, which typically refers to a country/region. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region` throughout the documentation and parameter naming.

38	azps-14.6.0\Az.DataBox\Update-AzDataBoxJob.md	country	108	2	Replacement required	Geopolitical	Details The term `country` is used as a property in an object representing a shipping address, which is effectively labeling a country/region field. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.

39	azps-14.6.0\Az.Site\Update-AzSite.md	country	117	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name to specify the country of an address. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.
40	azps-14.6.0\Az.Site\Update-AzSite.md	country	118	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter to specify the address of a site, which may refer to a geopolitical entity. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.

41	azps-14.6.0\Az.Site\New-AzSite.md	country	20	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and in documentation to specify the address of a site. In this context, it is labeling a country/region field and should be updated to avoid geopolitical issues. The recommended change is to replace `country` with `country/region` wherever it is used as a label or parameter.
42	azps-14.6.0\Az.Site\New-AzSite.md	country	46	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and in documentation to indicate the location of a site, which can be interpreted as labeling a country/region resource. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region` throughout the documentation and parameter definitions.
43	azps-14.6.0\Az.Site\New-AzSite.md	country	53	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and in documentation to specify the address of a site, which can refer to either a country or a region. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region` throughout the documentation and parameter definitions.
44	azps-14.6.0\Az.Site\New-AzSite.md	country	66	2	Replacement required	Geopolitical	Details The term `country` is used as a field/property name in a JSON configuration for site address information. According to the rules, when labeling a country/region list or similar resource, it should be replaced to avoid geopolitical issues. The field is not a legacy code or a forbidden term example, so the replacement is needed. Suggest replacing it with `country/region`.
45	azps-14.6.0\Az.Site\New-AzSite.md	country	124	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name to specify the country of an address, which can be interpreted as labeling a country/region resource. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.

46	azps-14.6.0\Az.SecurityInsights\Get-AzSentinelEnrichment.md	country	72	2	Replacement required	Geopolitical	Details The term `country` is used as a field label in the output of a command, representing a geopolitical entity. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.

47	azps-14.6.0\Az.Resources\Update-AzADUser.md	country	21	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name to indicate the user's location, which can refer to either a country or a region. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.
48	azps-14.6.0\Az.Resources\Update-AzADUser.md	country	182	2	No action needed	Geopolitical	Details The term `country` is used as a field/property name in a parameter list for a PowerShell cmdlet, which is a technical context referring to a database or API field. According to the rules, when referring to a field or filter name, it does not need to be replaced or removed.

49	azps-14.6.0\Az.Resources\New-AzADUser.md	country	21	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name to indicate the user's location, and the description refers to 'country/region' as the intended meaning. To avoid geopolitical issues and ensure inclusivity, it should be replaced with 'country/region'.

50	azps-14.6.0\Az.Purview\Get-AzPurviewScanRuleset.md	Turkey	43	2	Replacement required	Geopolitical	Details The term `Turkey` is used as part of a system classification label referring to the country/region, not the bird. To avoid geopolitical issues and follow current naming conventions, it should be replaced with `Türkiye`.

This comment lists only the first 50 of 223 issues due to GitHub's comment length limit.

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

learn-build-service-prod · 2025-11-03T19:56:57Z

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

#	File	Term	Line	Sev	AI Recommendation	Class	AI Review Details
1	azps-14.6.0\Az.Support\Update-AzSupportTicket.md	country	134	2	Replacement required	Geopolitical	Details The term `country` is used to describe a user attribute in a parameter description, which is likely to be used for filtering or identifying user location. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.

2	azps-14.6.0\Az.Support\Update-AzSupportTicketsNoSubscription.md	country	131	2	Replacement required	Geopolitical	Details The term `country` is used to label a field for user information, which may refer to a country or region. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.

3	azps-14.6.0\Az.Site\New-AzSite.md	country	20	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and label for address information in a public API and documentation. To avoid geopolitical issues and ensure inclusivity, it should be updated to `country/region` throughout the documentation and parameter descriptions.
4	azps-14.6.0\Az.Site\New-AzSite.md	country	33	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and in example usage to specify the address of a site. To avoid geopolitical issues and be inclusive of regions that may not be recognized as countries, it should be replaced with `country/region` throughout the documentation and parameter definitions.
5	azps-14.6.0\Az.Site\New-AzSite.md	country	46	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and in documentation to indicate the geographic location of a site. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region` throughout the documentation and parameter definitions.
6	azps-14.6.0\Az.Site\New-AzSite.md	country	53	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and in documentation to specify the address of a site, which can refer to geopolitical entities. To avoid geopolitical issues and be inclusive of regions that may not be recognized as countries, it should be replaced with `country/region` throughout the documentation and parameter naming.
7	azps-14.6.0\Az.Site\New-AzSite.md	country	66	2	Replacement required	Geopolitical	Details The term `country` is used as a field name in a JSON object representing an address, which is labeling a country/region resource. To avoid geopolitical issues and follow inclusive terminology, it should be replaced with `country/region`.
8	azps-14.6.0\Az.Site\New-AzSite.md	country	74	2	Replacement required	Geopolitical	Details The term `country` is used as a label in a JSON object for site address information, which is a scenario where geopolitical sensitivity is relevant. To avoid issues, it should be replaced with `country/region`.
9	azps-14.6.0\Az.Site\New-AzSite.md	country	87	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and in example usage to specify the address of a site. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region` throughout the documentation, including parameter names and descriptions.
10	azps-14.6.0\Az.Site\New-AzSite.md	country	124	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and description to specify the country of an address. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region` throughout the documentation and parameter naming.
11	azps-14.6.0\Az.Site\New-AzSite.md	country	125	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and description for specifying the address of a site. In this context, it is labeling a field that may refer to either a country or a region, and to avoid geopolitical issues, it should be replaced with `country/region`.

12	azps-14.6.0\Az.Security\Get-AzSecurityAdaptiveApplicationControl.md	whitelist	34	2	No action needed	Diversity	Details The term `whitelist` appears only as a component of resource type and property names, such as 'applicationWhitelistings' and not as a standalone label or description. According to the rules, when the word is a component of other words (e.g., in resource names, file paths, or property names), it does not need to be replaced or removed.
13	azps-14.6.0\Az.Security\Get-AzSecurityAdaptiveApplicationControl.md	whitelist	36	2	No action needed	Diversity	Details The term `whitelist` appears as a component of resource type names and file paths (e.g., applicationWhitelistings, /applicationWhitelistings/GROUP2), which are industry-standard naming conventions and technical identifiers. According to the rules, when industry naming conventions or consistency make replacement of the term impractical, the term should be left unchanged.
14	azps-14.6.0\Az.Security\Get-AzSecurityAdaptiveApplicationControl.md	whitelist	40	2	No action needed	Diversity	Details The term `whitelist` appears as a component of resource type names and IDs, such as 'applicationWhitelistings', which are part of Azure's established naming conventions and resource identifiers. According to the rules, when industry naming conventions or consistency make replacement of the term impractical, it should be left unchanged.
15	azps-14.6.0\Az.Security\Get-AzSecurityAdaptiveApplicationControl.md	whitelist	42	2	No action needed	Diversity	Details The term `whitelist` appears as a component of resource type names and property names (such as applicationWhitelistings and Microsoft.Security/applicationWhitelistings), which are part of legacy code and industry-standard naming conventions. According to the rules, when industry naming conventions or consistency make replacement of the term impractical, it should be left unchanged.
16	azps-14.6.0\Az.Security\Get-AzSecurityAdaptiveApplicationControl.md	whitelist	46	2	No action needed	Diversity	Details The term `whitelist` appears as a component of resource type names and IDs, such as 'applicationWhitelistings', which are part of Azure's established naming conventions and resource identifiers. According to the rules, when industry naming conventions or consistency make replacement of the term impractical, it should be left unchanged.
17	azps-14.6.0\Az.Security\Get-AzSecurityAdaptiveApplicationControl.md	whitelist	48	2	No action needed	Diversity	Details The term `whitelist` appears only as a component of resource type names and file paths (e.g., applicationWhitelistings, /applicationWhitelistings/GROUP2), which are technical identifiers and not user-facing descriptive text. According to the rules, when the word is a component of other words or appears in file paths, it does not need to be replaced or removed.

18	azps-14.6.0\Az.Resources\New-AzADUser.md	country	37	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name to indicate the user's location, and the description also refers to 'country/region'. To avoid geopolitical issues and ensure consistency, the parameter name should be updated to `country/region`.
19	azps-14.6.0\Az.Resources\New-AzADUser.md	country	191	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name to indicate the user's location, and the description refers to 'country/region'. To avoid geopolitical issues and ensure inclusivity, it should be updated to `country/region` for consistency with best practices and the guidance provided.
20	azps-14.6.0\Az.Resources\New-AzADUser.md	countries	830	2	Replacement required	Geopolitical	Details The term `countries` is used to describe the availability of services for users based on their location, which is a scenario where geopolitical sensitivity is important. To avoid issues, it should be replaced with `countries/regions` or a similar expression.

21	azps-14.6.0\Az.Peering\Get-AzPeeringServiceLocation.md	country	61	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and in documentation to label a filter for peering service locations by country. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region` throughout the documentation and parameter naming.
22	azps-14.6.0\Az.Peering\Get-AzPeeringServiceLocation.md	country	65	2	Replacement required	Geopolitical	Details The term `country` is used to label a column in a table and as a parameter name to filter locations, which is effectively labeling a country/region list or resource. To avoid geopolitical issues, it should be replaced with `country/region` throughout the documentation, including the parameter name and table column.
23	azps-14.6.0\Az.Peering\Get-AzPeeringServiceLocation.md	country	84	2	Replacement required	Geopolitical	Details The term `country` is used to label a filter and describe a list of locations grouped by country, which is a scenario where geopolitical sensitivity applies. To avoid issues, it should be replaced with `country/region` throughout the documentation, including parameter names and descriptions.
24	azps-14.6.0\Az.Peering\Get-AzPeeringServiceLocation.md	country	88	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name and description to filter or label a list of locations, which can be interpreted as labeling a country/region list or resource. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region` throughout the parameter name and description.
25	azps-14.6.0\Az.Peering\Get-AzPeeringServiceLocation.md	country	89	2	Replacement required	Geopolitical	Details The term `country` is used to label a parameter that filters locations by country, which is a scenario where geopolitical sensitivity applies. To avoid issues, it should be replaced with `country/region` for inclusivity and accuracy.

26	docs-conceptual\azps-14.6.0\release-notes-azureps.md	whitelist	5788	2	No action needed	Diversity	Details The term `whitelist` appears in the context of describing Azure PowerShell release notes and is used in the phrase 'allow-listed by the service to use IP/Service Tag ACL features.' This usage aligns with industry naming conventions and is not being used to describe a list of people or things that have received approval, but rather as a technical term in a legacy or industry-standard context. Therefore, replacement is not required.
27	docs-conceptual\azps-14.6.0\release-notes-azureps.md	whitelist	8371	2	No action needed	Diversity	Details The term `whitelist` appears in the context of a release note describing a technical requirement: 'Subscriptions must be allow-listed by the service to use IP/Service Tag ACL features.' In this context, it is used as part of industry-standard terminology for access control lists (ACLs), and changing it may cause confusion or inconsistency with established documentation and APIs. The rules specify that when industry naming conventions or consistency make replacement of the term impractical, the term should be left unchanged.

28	docs-conceptual\azps-14.6.0\migrate-az-12.0.0.md	country	2554	2	Replacement required	Geopolitical	Details The term `country` is used as a field/property name in a parameter object for a PowerShell cmdlet, specifically to indicate the user's country in support ticket creation. To avoid geopolitical issues and follow Microsoft guidance, it should be replaced with `country/region` or the updated parameter name as shown in the 'After' examples (e.g., `ContactDetailCountry`).
29	docs-conceptual\azps-14.6.0\migrate-az-12.0.0.md	country	2556	2	Replacement required	Geopolitical	Details The term `country` is used as a key in a parameter object to specify a user's country in a support ticket creation scenario. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region` or a similar expression. This aligns with the guidance to update such terms in user-facing fields.

30	azps-14.6.0\Az.Site\Update-AzSite.md	country	20	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name to specify the country of an address. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.
31	azps-14.6.0\Az.Site\Update-AzSite.md	country	117	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name to specify the country of an address. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.
32	azps-14.6.0\Az.Site\Update-AzSite.md	country	118	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter to specify the address of a site, which may refer to geopolitical entities. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.

33	azps-14.6.0\Az.Security\Get-AzSecurityAdaptiveApplicationControlGroup.md	whitelist	34	2	No action needed	Diversity	Details The term `whitelist` appears as a component of resource type and property names such as 'applicationWhitelistings' and 'Microsoft.Security/applicationWhitelistings'. According to the guidelines, when the word is a component of other words, such as in resource names, it does not need to be replaced or removed.
34	azps-14.6.0\Az.Security\Get-AzSecurityAdaptiveApplicationControlGroup.md	whitelist	36	2	No action needed	Diversity	Details The term `whitelist` appears as a component of resource type and property names such as 'applicationWhitelistings' and 'Microsoft.Security/applicationWhitelistings'. According to the guidelines, when the word is a component of other words, such as in resource names, it does not need to be replaced or removed.

35	azps-14.6.0\Az.Resources\Update-AzADUser.md	country	37	2	No action needed	Geopolitical	Details The term `country` is used as a parameter name in a PowerShell cmdlet, which is a field/property name. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.
36	azps-14.6.0\Az.Resources\Update-AzADUser.md	country	53	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name to indicate the user's location, which can be interpreted as labeling a country/region resource. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.
37	azps-14.6.0\Az.Resources\Update-AzADUser.md	country	69	2	Replacement required	Geopolitical	Details The term `country` is used as a parameter name to indicate the user's location, which can be interpreted as labeling a country/region resource. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.
38	azps-14.6.0\Az.Resources\Update-AzADUser.md	country	182	2	No action needed	Geopolitical	Details The term `country` is used as a field/parameter name in a PowerShell cmdlet, which is considered a property name. According to the rules, when referring to a field or filter name, database name, parameter name, panel name, property name, file name or similar, it does not need to be replaced or removed.
39	azps-14.6.0\Az.Resources\Update-AzADUser.md	countries	771	2	Replacement required	Geopolitical	Details The term `countries` is used to refer to a list of locations for legal requirements regarding service availability. To avoid geopolitical issues, it should be replaced with `countries/regions`.

40	azps-14.6.0\Az.Peering\Get-AzPeeringServiceCountry.md	countries	13	2	Replacement required	Geopolitical	Details The term `countries` is used to label a list of geographic locations for a service, which can raise geopolitical sensitivity. It should be replaced with `countries/regions` to be inclusive and avoid issues.
41	azps-14.6.0\Az.Peering\Get-AzPeeringServiceCountry.md	countries	27	2	Replacement required	Geopolitical	Details The term `countries` is used to label a list of geographic locations for a service, which can raise geopolitical sensitivity. It should be replaced with `countries/regions` to be inclusive and avoid issues.
42	azps-14.6.0\Az.Peering\Get-AzPeeringServiceCountry.md	Hong Kong	43	2	Replacement required	Geopolitical	Details The term `Hong Kong` is used as an entry in a list of countries for a service, which is a formal context. To avoid geopolitical issues and ensure accuracy, it should be replaced with `Hong Kong SAR` or `Hong Kong Special Administrative Region`.

43	azps-14.6.0\Az.Oracle\Update-AzOracleAutonomousDatabase.md	whitelist	58	2	No action needed	Diversity	Details The term `whitelist` is used as part of a parameter name (`WhitelistedIP`) in a PowerShell cmdlet, which is a field/property name in code. According to the rules, when referring to a field or parameter name, it does not need to be replaced or removed.

44	azps-14.6.0\Az.TrustedSigning\New-AzTrustedSigningCertificateProfile.md	country	51	2	Replacement required	Geopolitical	Details The term `country` is used as a column header in a table output, representing a geographic location. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.

45	azps-14.6.0\Az.TrustedSigning\Get-AzTrustedSigningCertificateProfile.md	country	55	2	Replacement required	Geopolitical	Details The term `country` is used as a column header in a data output table, which labels a country/region field. To avoid geopolitical issues and follow inclusive language guidelines, it should be replaced with `country/region`.
46	azps-14.6.0\Az.TrustedSigning\Get-AzTrustedSigningCertificateProfile.md	country	68	2	Replacement required	Geopolitical	Details The term `country` is used as a column header in a table that lists certificate profile details, which is effectively labeling a country/region field. To avoid geopolitical issues, it should be replaced with `country/region`.

47	azps-14.6.0\Az.Support\New-AzSupportTicket.md	country	267	2	Replacement required	Geopolitical	Details The term `country` is used to label a parameter that collects the user's country information, which is effectively labeling a country/region list or resource. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.

48	azps-14.6.0\Az.Support\New-AzSupportTicketsNoSubscription.md	country	145	2	Replacement required	Geopolitical	Details The term `country` is used to label a parameter that collects the user's country information. To avoid geopolitical issues and be inclusive of regions, it should be replaced with `country/region`. Specifically, update the parameter and its description to use `country/region` instead of just `country`.

49	azps-14.6.0\Az.SecurityInsights\Get-AzSentinelEnrichment.md	country	72	2	Replacement required	Geopolitical	Details The term `country` is used as a field label in the output of a command, representing a geopolitical entity. To avoid geopolitical issues and ensure inclusivity, it should be replaced with `country/region`.

50	azps-14.6.0\Az.Purview\Get-AzPurviewScanRuleset.md	Turkey	43	2	Replacement required	Geopolitical	Details The term `Turkey` is used as part of a system classification referring to the country/region, not the bird. To align with current geopolitical naming conventions, it should be replaced with `Türkiye`.

This comment lists only the first 50 of 223 issues due to GitHub's comment length limit.

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

learn-build-service-prod · 2025-11-03T20:20:22Z

Learn Build status updates of commit 3fcee57:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
azps-14.6.0/Az.Advisor/Get-AzAdvisorRecommendation.md	⚠️Warning	View (azps-14.6.0)	Details
azps-14.6.0/Az.DataLakeStore/Az.DataLakeStore.md	⚠️Warning	View (azps-14.6.0)	Details
azps-14.6.0/Az.KeyVault/Az.KeyVault.md	⚠️Warning	View (azps-14.6.0)	Details
azps-14.6.0/Az.NetAppFiles/Az.NetAppFiles.md	⚠️Warning	View (azps-14.6.0)	Details
azps-14.6.0/Az.Network/Az.Network.md	⚠️Warning	View (azps-14.6.0)	Details
azps-14.6.0/Az.Search/Az.Search.md	⚠️Warning	View (azps-14.6.0)	Details
azps-14.6.0/Az.SignalR/Az.SignalR.md	⚠️Warning	View (azps-14.6.0)	Details
azps-14.6.0/Az.AksArc/New-AzAksArcCluster.md	💡Suggestion	View (azps-14.6.0)	Details
azps-14.6.0/Az.AksArc/Update-AzAksArcCluster.md	💡Suggestion	View (azps-14.6.0)	Details
azps-14.6.0/Az.ApiManagement/Get-AzApiManagementAuthorizationServer.md	💡Suggestion	View (azps-14.6.0)	Details
azps-14.6.0/Az.ApiManagement/Remove-AzApiManagementRegion.md	💡Suggestion	View (azps-14.6.0)	Details
azps-14.6.0/Az.ApplicationInsights/Get-AzApplicationInsights.md	💡Suggestion	View (azps-14.6.0)	Details
azps-14.6.0/Az.ApplicationInsights/Set-AzApplicationInsightsContinuousExport.md	💡Suggestion	View (azps-14.6.0)	Details
azps-14.6.0/Az.Accounts/Add-AzEnvironment.md	✅Succeeded	View (azps-14.6.0)
azps-14.6.0/Az.Accounts/Az.Accounts.md	✅Succeeded	View (azps-14.6.0)
azps-14.6.0/Az.Accounts/Clear-AzConfig.md	✅Succeeded	View (azps-14.6.0)
azps-14.6.0/Az.Accounts/Clear-AzContext.md	✅Succeeded	View (azps-14.6.0)
azps-14.6.0/Az.Accounts/Clear-AzDefault.md	✅Succeeded	View (azps-14.6.0)
azps-14.6.0/Az.Accounts/Connect-AzAccount.md	✅Succeeded	View (azps-14.6.0)
azps-14.6.0/Az.Accounts/Disable-AzContextAutosave.md	✅Succeeded	View (azps-14.6.0)
azps-14.6.0/Az.Accounts/Disable-AzDataCollection.md	✅Succeeded	View (azps-14.6.0)
azps-14.6.0/Az.Accounts/Disable-AzureRmAlias.md	✅Succeeded	View (azps-14.6.0)
azps-14.6.0/Az.Accounts/Disconnect-AzAccount.md	✅Succeeded	View (azps-14.6.0)
azps-14.6.0/Az.Accounts/Enable-AzContextAutosave.md	✅Succeeded	View (azps-14.6.0)
azps-14.6.0/Az.Accounts/Enable-AzDataCollection.md	✅Succeeded	View (azps-14.6.0)

This comment lists only the first 25 files in the pull request.

azps-14.6.0/Az.Advisor/Get-AzAdvisorRecommendation.md

Line 0, Column 0: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#category' in 'azps-14.6.0/Az.Advisor/Get-AzAdvisorRecommendation.yml', did you mean '#-category'?

azps-14.6.0/Az.DataLakeStore/Az.DataLakeStore.md

Line 0, Column 0: [Warning: PSMD2Yaml_InconsistentCmdletsInModule] Inconsistent cmdlets found in module: Az.DataLakeStore. 1 cmdlets in the module folder but not listed in the module file: Get-AzDataLakeStoreDeletedItemsWithToken.

azps-14.6.0/Az.KeyVault/Az.KeyVault.md

Line 0, Column 0: [Warning: PSMD2Yaml_InconsistentCmdletsInModule] Inconsistent cmdlets found in module: Az.KeyVault. 4 cmdlets in the module folder but not listed in the module file: Add-AzKeyVaultManagedHsmNetworkRule, New-AzKeyVaultManagedHsmNetworkRuleSetObject, Remove-AzKeyVaultManagedHsmNetworkRule, Update-AzKeyVaultManagedHsmNetworkRuleSet.

azps-14.6.0/Az.NetAppFiles/Az.NetAppFiles.md

Line 0, Column 0: [Warning: PSMD2Yaml_InconsistentCmdletsInModule] Inconsistent cmdlets found in module: Az.NetAppFiles. 1 cmdlets in the module folder but not listed in the module file: Split-AzNetAppFilesCloneFromParent.

azps-14.6.0/Az.Network/Az.Network.md

Line 0, Column 0: [Warning: PSMD2Yaml_InconsistentCmdletsInModule] Inconsistent cmdlets found in module: Az.Network. 1 cmdlets in the module folder but not listed in the module file: New-AzVirtualNetworkGatewayCertificateAuthentication.

azps-14.6.0/Az.Search/Az.Search.md

Line 0, Column 0: [Warning: PSMD2Yaml_InconsistentCmdletsInModule] Inconsistent cmdlets found in module: Az.Search. 1 cmdlets in the module folder but not listed in the module file: Invoke-AzSearchServiceUpgrade.

azps-14.6.0/Az.SignalR/Az.SignalR.md

Line 0, Column 0: [Warning: PSMD2Yaml_InconsistentCmdletsInModule] Inconsistent cmdlets found in module: Az.SignalR. 3 cmdlets in the module folder but not listed in the module file: Add-AzSignalRNetworkIpRule, New-AzSignalRNetworkIpRuleObject, Remove-AzSignalRNetworkIpRule.

azps-14.6.0/Az.AksArc/New-AzAksArcCluster.md

Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Az.AksArc.New-AzAksArcCluster cmdlet. Parameters lacking description: AdminGroupObjectID, EnableAutoScaling, Location, MaxCount, MaxPod, MinCount

azps-14.6.0/Az.AksArc/Update-AzAksArcCluster.md

Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Az.AksArc.Update-AzAksArcCluster cmdlet. Parameters lacking description: AdminGroupObjectID

azps-14.6.0/Az.ApiManagement/Get-AzApiManagementAuthorizationServer.md

Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Az.ApiManagement.Get-AzApiManagementAuthorizationServer cmdlet. Parameters lacking description: Context, ServerId

azps-14.6.0/Az.ApiManagement/Remove-AzApiManagementRegion.md

Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Az.ApiManagement.Remove-AzApiManagementRegion cmdlet. Parameters lacking description: DefaultProfile

azps-14.6.0/Az.ApplicationInsights/Get-AzApplicationInsights.md

Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Az.ApplicationInsights.Get-AzApplicationInsights cmdlet. Parameters lacking description: Full

azps-14.6.0/Az.ApplicationInsights/Set-AzApplicationInsightsContinuousExport.md

Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Az.ApplicationInsights.Set-AzApplicationInsightsContinuousExport cmdlet. Parameters lacking description: DisableConfiguration

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

learn-build-service-prod · 2025-11-03T21:01:26Z

Learn Build status updates of commit 3fcee57:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
azps-14.6.0/Az.Advisor/Get-AzAdvisorRecommendation.md	⚠️Warning	View (azps-14.6.0)	Details
azps-14.6.0/Az.DataLakeStore/Az.DataLakeStore.md	⚠️Warning	View (azps-14.6.0)	Details
azps-14.6.0/Az.KeyVault/Az.KeyVault.md	⚠️Warning	View (azps-14.6.0)	Details
azps-14.6.0/Az.NetAppFiles/Az.NetAppFiles.md	⚠️Warning	View (azps-14.6.0)	Details
azps-14.6.0/Az.Network/Az.Network.md	⚠️Warning	View (azps-14.6.0)	Details
azps-14.6.0/Az.Search/Az.Search.md	⚠️Warning	View (azps-14.6.0)	Details
azps-14.6.0/Az.SignalR/Az.SignalR.md	⚠️Warning	View (azps-14.6.0)	Details
azps-14.6.0/Az.AksArc/New-AzAksArcCluster.md	💡Suggestion	View (azps-14.6.0)	Details
azps-14.6.0/Az.AksArc/Update-AzAksArcCluster.md	💡Suggestion	View (azps-14.6.0)	Details
azps-14.6.0/Az.ApiManagement/Get-AzApiManagementAuthorizationServer.md	💡Suggestion	View (azps-14.6.0)	Details
azps-14.6.0/Az.ApiManagement/Remove-AzApiManagementRegion.md	💡Suggestion	View (azps-14.6.0)	Details
azps-14.6.0/Az.ApplicationInsights/Get-AzApplicationInsights.md	💡Suggestion	View (azps-14.6.0)	Details
azps-14.6.0/Az.ApplicationInsights/Set-AzApplicationInsightsContinuousExport.md	💡Suggestion	View (azps-14.6.0)	Details
azps-14.6.0/Az.Accounts/Add-AzEnvironment.md	✅Succeeded	View (azps-14.6.0)
azps-14.6.0/Az.Accounts/Az.Accounts.md	✅Succeeded	View (azps-14.6.0)
azps-14.6.0/Az.Accounts/Clear-AzConfig.md	✅Succeeded	View (azps-14.6.0)
azps-14.6.0/Az.Accounts/Clear-AzContext.md	✅Succeeded	View (azps-14.6.0)
azps-14.6.0/Az.Accounts/Clear-AzDefault.md	✅Succeeded	View (azps-14.6.0)
azps-14.6.0/Az.Accounts/Connect-AzAccount.md	✅Succeeded	View (azps-14.6.0)
azps-14.6.0/Az.Accounts/Disable-AzContextAutosave.md	✅Succeeded	View (azps-14.6.0)
azps-14.6.0/Az.Accounts/Disable-AzDataCollection.md	✅Succeeded	View (azps-14.6.0)
azps-14.6.0/Az.Accounts/Disable-AzureRmAlias.md	✅Succeeded	View (azps-14.6.0)
azps-14.6.0/Az.Accounts/Disconnect-AzAccount.md	✅Succeeded	View (azps-14.6.0)
azps-14.6.0/Az.Accounts/Enable-AzContextAutosave.md	✅Succeeded	View (azps-14.6.0)
azps-14.6.0/Az.Accounts/Enable-AzDataCollection.md	✅Succeeded	View (azps-14.6.0)

This comment lists only the first 25 files in the pull request.

azps-14.6.0/Az.Advisor/Get-AzAdvisorRecommendation.md

Line 0, Column 0: [Warning: bookmark-not-found - See documentation] Cannot find bookmark '#category' in 'azps-14.6.0/Az.Advisor/Get-AzAdvisorRecommendation.yml', did you mean '#-category'?

azps-14.6.0/Az.DataLakeStore/Az.DataLakeStore.md

Line 0, Column 0: [Warning: PSMD2Yaml_InconsistentCmdletsInModule] Inconsistent cmdlets found in module: Az.DataLakeStore. 1 cmdlets in the module folder but not listed in the module file: Get-AzDataLakeStoreDeletedItemsWithToken.

azps-14.6.0/Az.KeyVault/Az.KeyVault.md

Line 0, Column 0: [Warning: PSMD2Yaml_InconsistentCmdletsInModule] Inconsistent cmdlets found in module: Az.KeyVault. 4 cmdlets in the module folder but not listed in the module file: Add-AzKeyVaultManagedHsmNetworkRule, New-AzKeyVaultManagedHsmNetworkRuleSetObject, Remove-AzKeyVaultManagedHsmNetworkRule, Update-AzKeyVaultManagedHsmNetworkRuleSet.

azps-14.6.0/Az.NetAppFiles/Az.NetAppFiles.md

Line 0, Column 0: [Warning: PSMD2Yaml_InconsistentCmdletsInModule] Inconsistent cmdlets found in module: Az.NetAppFiles. 1 cmdlets in the module folder but not listed in the module file: Split-AzNetAppFilesCloneFromParent.

azps-14.6.0/Az.Network/Az.Network.md

Line 0, Column 0: [Warning: PSMD2Yaml_InconsistentCmdletsInModule] Inconsistent cmdlets found in module: Az.Network. 1 cmdlets in the module folder but not listed in the module file: New-AzVirtualNetworkGatewayCertificateAuthentication.

azps-14.6.0/Az.Search/Az.Search.md

Line 0, Column 0: [Warning: PSMD2Yaml_InconsistentCmdletsInModule] Inconsistent cmdlets found in module: Az.Search. 1 cmdlets in the module folder but not listed in the module file: Invoke-AzSearchServiceUpgrade.

azps-14.6.0/Az.SignalR/Az.SignalR.md

Line 0, Column 0: [Warning: PSMD2Yaml_InconsistentCmdletsInModule] Inconsistent cmdlets found in module: Az.SignalR. 3 cmdlets in the module folder but not listed in the module file: Add-AzSignalRNetworkIpRule, New-AzSignalRNetworkIpRuleObject, Remove-AzSignalRNetworkIpRule.

azps-14.6.0/Az.AksArc/New-AzAksArcCluster.md

Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Az.AksArc.New-AzAksArcCluster cmdlet. Parameters lacking description: AdminGroupObjectID, EnableAutoScaling, Location, MaxCount, MaxPod, MinCount

azps-14.6.0/Az.AksArc/Update-AzAksArcCluster.md

Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Az.AksArc.Update-AzAksArcCluster cmdlet. Parameters lacking description: AdminGroupObjectID

azps-14.6.0/Az.ApiManagement/Get-AzApiManagementAuthorizationServer.md

Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Az.ApiManagement.Get-AzApiManagementAuthorizationServer cmdlet. Parameters lacking description: Context, ServerId

azps-14.6.0/Az.ApiManagement/Remove-AzApiManagementRegion.md

Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Az.ApiManagement.Remove-AzApiManagementRegion cmdlet. Parameters lacking description: DefaultProfile

azps-14.6.0/Az.ApplicationInsights/Get-AzApplicationInsights.md

Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Az.ApplicationInsights.Get-AzApplicationInsights cmdlet. Parameters lacking description: Full

azps-14.6.0/Az.ApplicationInsights/Set-AzApplicationInsightsContinuousExport.md

Line 0, Column 0: [Suggestion: PSMD2Yaml_ContentMissing] Missing content in Az.ApplicationInsights.Set-AzApplicationInsightsContinuousExport cmdlet. Parameters lacking description: DisableConfiguration

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

mikefrobbins

LGTM

mikefrobbins · 2025-11-07T14:20:33Z

#policheck-false-positive

Azure PowerShell includes several commands that use terms such as "Country" and "Whitelist" in their parameter names. PoliCheck is incorrectly flagging the autogenerated reference documentation for these commands.

docsreference@microsoft.com and others added 2 commits October 30, 2025 15:40

CI Update

c6b6c48

Build.Reason:Manual by Huaping Yu (BEYONDSOFT CONSULTING INC) Build.Url:https://apidrop.visualstudio.com/Content%20CI/_build/results?buildId=574961&view=results

update CI build for azps-14.6.0

3fcee57

huypub requested a review from mikefrobbins as a code owner November 3, 2025 19:39

huypub closed this Nov 3, 2025

huypub reopened this Nov 3, 2025

mikefrobbins approved these changes Nov 3, 2025

View reviewed changes

huypub merged commit fb242c7 into main Nov 4, 2025
5 of 9 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

CI of azps-14.6.0 #3740

CI of azps-14.6.0 #3740

Uh oh!

huypub commented Nov 3, 2025 •

edited

Loading

Uh oh!

learn-build-service-prod bot commented Nov 3, 2025

Uh oh!

learn-build-service-prod bot commented Nov 3, 2025

Uh oh!

learn-build-service-prod bot commented Nov 3, 2025

Uh oh!

learn-build-service-prod bot commented Nov 3, 2025

Uh oh!

mikefrobbins left a comment

Uh oh!

Uh oh!

mikefrobbins commented Nov 7, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

CI of azps-14.6.0 #3740

CI of azps-14.6.0 #3740

Uh oh!

Conversation

huypub commented Nov 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Summary

PR Checklist

Uh oh!

learn-build-service-prod bot commented Nov 3, 2025

PoliCheck Scan Report

More information about PoliCheck

Uh oh!

learn-build-service-prod bot commented Nov 3, 2025

PoliCheck Scan Report

More information about PoliCheck

Uh oh!

learn-build-service-prod bot commented Nov 3, 2025

⚠️ Validation status: warnings

Uh oh!

learn-build-service-prod bot commented Nov 3, 2025

⚠️ Validation status: warnings

Uh oh!

mikefrobbins left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

mikefrobbins commented Nov 7, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

huypub commented Nov 3, 2025 •

edited

Loading